5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
- Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-3: Data Dictionary

Fields and Field Types


Fields represent the smallest units of data storage in an APPX application. Each field contains an item of information in a database. While a domain establishes a set of common attributes (such as required physical storage space) for one or more fields, it is the field that is used to store application data. The data information stored in a field is referred to as a field value. Fields are grouped together as records stored within files.

There are thirteen types of fields in the APPX data dictionary:

Domain fields are fields that directly express the attributes defined in a domain while they define and occupy new physical space in a file. There are nine distinct domain-type fields: Alpha, Format, System, Text, Token, Date, Logic, Numeric, and Same As. Refer to the Domains and Domain Types section for additional information. You can choose to set up physical fields to exclusively reference domains, or you can set up individual field types directly.

Alpha fields are comprised of numbers, letters, and special characters (-, #, or &, for example).

Format fields are like alpha fields except that an edit mask is the primary characteristic.

System fields, often referred to as audit fields, display data that is provided by the system.

Text fields allow the user to enter blocks of text on the data entry screen.

Token fields are like alpha fields, except that they have specific values that are stored as corresponding numbers.

Numeric fields are restricted to number, decimal (.), and sign (-) entries.

Date fields are patterns for fields that contain dates and/or times, from centuries through hundredths of a second.

Logic fields are fields with possible values of yes or no , or to represent an unknown value (Y, N, or blank using Character Mode).

Synonym fields provide alternative names for referencing existing APPX fields. They occupy no physical space in a file aside from the fields they reference.

Substring fields represent discrete portions of longer alphanumeric fields. They occupy no physical space in a file aside from the fields they are a part of.

Group header fields are used to group other fields by identifying the beginning and ending fields in a group of fields. The group can then be referenced by the name of the group header field. Group headers occupy no physical space in a file aside from the fields that comprise the group.

Group trailer fields are optional placeholders to allow for terminating a group without referencing a physical field. They provide a streamlined method to allow for additions to the end of groups. They also provide visual clues as to the ends of groups when scanning the Data Dictionary. Group trailers occupy no physical space in files.

Application Design Manual                                         "Powered by Appx Software"

41

©2006 By APPX Software, Inc. All Rights Reserved